Use HTTPS and your own API credentials. POST examples keep credentials out of URL paths. The older positional GET format remains supported, but credentials in URLs can appear in logs and browser history.
Description:
Send a text (SMS) or multi-media message (MMS)
URI:
https://api.multitel.net/v3/sendsms
Parameters:
Required: from is your messaging-enabled number; to is the destination number. Supply nonempty text, base64-encoded media, or both. For MMS, media is a JPEG or PNG image. Optional notifyurl receives status updates; reference is your own identifier for matching those updates to a message. Acceptance into the queue is not confirmation of delivery. Example costs are illustrative; actual charges depend on the route, message type and segment count.
Methods:
POST
Sample Output:
{
"status":
{
"code":"200",
"msg":""
},
"response":
{
"status":"Success",
"message":"Message queued",
"causecode":0,
"uniqueid":"eba01f56-1fbe-4aac-9ff7-4a6b9e00001",
"cost":0.015,
"chars":0,
"parts":1,
"permsg":0.015,
"pid":"ZQF88E7031eba01f56-1fbe-4aac-9ff7-4a6b9e00001"
}
}Sample code:
curl --fail-with-body --show-error \ --request POST \ --user "$MULTITEL_API_USERNAME:$MULTITEL_API_PASSWORD" \ "https://api.multitel.net/v3/sendsms" \ --data-urlencode "from=$MULTITEL_SMS_NUMBER" \ --data-urlencode "to=$MULTITEL_DESTINATION_NUMBER" \ --data-urlencode "text=Test message" \ --data-urlencode "reference=customer-message-001"